Expand All
Collapse All
<?xml version="1.0" encoding="UTF-8"?> <val> <!-- kbstaff sees everything, so include all audience-filtered content --> <prop action="include" att="audience" ></prop> </val>
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE task PUBLIC "urn:pubid:org.kuali.kits.kms:doctypes:dita:task"
"http://www.indiana.edu/~worklist/dita-prototypes/org.kuali.kits.kms/doctypes/task/dtd/kbtask.dtd">
<task audience="default" id="kbdoc">
<title id="default">How do I define the keys for all cross references in a topic in the DITA KB?</title>
<taskbody>
<steps>
<step>
<note audience="kbstaff">You need to run the xslt transformation</note>
<cmd>With the topic or associated map open in the editor window, in the toolbar, select
<uicontrol>Configure Transformation Scenario</uicontrol></cmd></step>
</steps>
</taskbody>
</task>./features/step_definitions/all_steps.rb:316 ./features/step_definitions/all_steps.rb:315:in `/^I should see "([^"]*)" in the preview window$/' features/audience-filtering.feature:34:in `Then I should see "You need to run the xslt transformation" in the preview window'
314 # from http://blog.kshitizgurung.info/2011/07/detecting-popup-window-and-implementing-test-on-in-capybara-selenium/
315 within_window(page.driver.browser.window_handles.last) do
316 page.should have_content(string)
317 end
318end<?xml version="1.0" encoding="UTF-8"?>
<val>
<prop action="exclude" att="audience" ></prop>
<prop action="include" att="audience" val="default" ></prop>
</val><?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE task PUBLIC "urn:pubid:org.kuali.kits.kms:doctypes:dita:task"
"http://www.indiana.edu/~worklist/dita-prototypes/org.kuali.kits.kms/doctypes/task/dtd/kbtask.dtd">
<task audience="default" id="kbdoc">
<title id="default">How do I define the keys for all cross references in a topic in the DITA KB?</title>
<taskbody>
<steps>
<step>
<note audience="kbstaff">You need to run the xslt transformation</note>
<cmd>With the topic or associated map open in the editor window, in the toolbar, select
<uicontrol>Configure Transformation Scenario</uicontrol></cmd></step>
</steps>
</taskbody>
</task>
In order to write about new things
As a KMS Maintainer
I want to create new content through the CRUD web interface
<task id="kbdoc"> <title id="default">In Microsoft Excel, how can I apply several formats to a cell in one step?</title> </task>
In order to work with content in the KMS
As a KMS Maintainer
I want to interact with the KMS through a web interface
In order to keep the repository uncluttered so users can find what they need
As a KMS Maintainer
I want to be able to delete existing documents
<topic id="ajpt-dmm2"> <title id="default">At IU, what is OneStart???</title> </topic>
(eval):2:in `send' (eval):2:in `click_link' ./features/step_definitions/web_steps.rb:35 ./features/step_definitions/web_steps.rb:14:in `with_scope' ./features/step_definitions/web_steps.rb:34:in `/^(?:|I )follow "([^"]*)"(?: within "([^"]*)")?$/' features/deleting-content.feature:18:in `And I follow "Delete content"'
0# Couldn't get snippet for (eval)
In order to know what existing documents contain
As a KMS Maintainer
I want to be able to read existing documents through the CRUD web interface
<topic id="kbdoc"> <title id="default">How can I contact the Support Center at each IU campus for help? </title> </topic>
features/reading-content.feature:17:in `When I view the document with filename "xxxx.dita"'
15</topic>
16"""
17When I view the document with filename "xxxx.dita"
18Then I should see "How can I contact the Support Center at each IU campus for help?" in the document text
19When /^I view the document with filename "([^"]*)"$/ do |arg1| pending # express the regexp above with the code you wish you had end
features/reading-content.feature:18:in `Then I should see "How can I contact the Support Center at each IU campus for help?" in the document text'
16"""
17When I view the document with filename "xxxx.dita"
18Then I should see "How can I contact the Support Center at each IU campus for help?" in the document text
19
20 Then /^I should see "([^"]*)" in the document text$/ do |arg1| pending # express the regexp above with the code you wish you had end
For Scenario 1, rendering a DITA-OT sample document, I've gotten it passing with actual new documents, using new filenames for every test, and just now it is also passing for recycled documents. To get the "Given a document with filename "xxxx.dita" exists with content" step group to actually complete creating the document I had to add a step to the end to wait for the page to finish reloading, because otherwise when there was another identical creation step group following it for the .ditamap file the first creation of the .dita file would not complete.
As far as the poller needing time to process the files, I've set the wait time as low as 5 seconds and still seen successful transformation. I've set it to 10 seconds for now.
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "http://docs.oasis-open.org/dita/v1.1/OS/dtd/topic.dtd">
<topic id="kbdoc" xml:lang="en-us">
<title>Shopping for groceries</title>
<shortdesc>Tips on buying groceries.</shortdesc>
<prolog>
<author type="creator">Tom McIntyre</author>
<copyright>
<copyryear year="2007" ></copyryear>
<copyrholder>Acme Company</copyrholder>
</copyright>
<critdates>
<created date="2006-August-07" ></created>
<revised modified="2007-March-18" ></revised>
</critdates>
<metadata>
<keywords>
<keyword>grocery shopping</keyword>
</keywords>
</metadata>
</prolog>
<body>
<p>A sample document to test ditac rendering.</p>
</body>
</topic><?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE map PUBLIC "-//OASIS//DTD DITA Map//EN" "http://docs.oasis-open.org/dita/v1.2/os/dtd1.2/technicalContent/dtd/map.dtd">
<map>
<topicref keys="xxaq" href="xxaq.dita#kbdoc"></topicref>
<reltable>
<relheader>
<relcolspec type="topic" linking="sourceonly">
<title>Source</title>
</relcolspec>
<relcolspec type="task" linking="targetonly">
<title>Refs</title>
</relcolspec>
<relcolspec type="glossentry" linking="targetonly">
<title>Hotitems</title>
</relcolspec>
</relheader>
<relrow>
<relcell>
<topicref keyref="xxaq"></topicref>
</relcell>
<relcell></relcell>
<relcell></relcell>
</relrow>
</reltable>
</map><?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE task PUBLIC "urn:pubid:org.kuali.kits.kms:doctypes:dita:task"
"http://www.indiana.edu/~worklist/dita-prototypes/org.kuali.kits.kms/doctypes/task/dtd/kbtask.dtd">
<task audience="default" id="kbdoc">
<title id="default">How do I define the keys for all cross references in a topic in the DITA KB?</title>
<shortdesc/>
<prolog>
<author>jorahood</author>
<critdates>
<created date=""/>
<revised modified=""/>
</critdates>
<metadata>
<keywords>
<keyword></keyword>
</keywords>
</metadata>
<docid id="bbah"/>
</prolog>
<taskbody>
<steps>
<step>
<note>You need to run the xslt transformation that will add key definitions for all the
refs in a map, as well as for all the kbhs, kbas, and boilers in the associated
topic.</note>
<cmd>With the topic or associated map open in the editor window, in the toolbar, select
<uicontrol>Configure Transformation Scenario</uicontrol></cmd></step>
<step>
<cmd>In the <wintitle>Scenario type</wintitle> dropdown, select <option>Xml Transformation
with XSLT</option>.</cmd>
</step>
<step>
<cmd>Under <wintitle>User Defined Scenarios</wintitle>, select
<option>contextualize</option> and click <uicontrol>Transform now</uicontrol>.</cmd>
<stepresult>The keys necessary to render the topic will appear at the bottom of the topic's ditamap.</stepresult>
</step>
</steps>
</taskbody>
</task><?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE map
PUBLIC "-//OASIS//DTD DITA Map//EN" "http://docs.oasis-open.org/dita/v1.2/os/dtd1.2/technicalContent/dtd/map.dtd">
<map id="kbdocmap">
<topicgroup id="docidbox"><topicref audience="default" keys="bbah" href="bbah.dita" id="docid"/></topicgroup>
<reltable>
<relheader>
<relcolspec linking="sourceonly">
<title>Source</title>
</relcolspec>
<relcolspec linking="targetonly">
<title>Refs</title>
</relcolspec>
</relheader>
<relrow>
<relcell>
<topicref keyref="bbah"/>
</relcell>
<relcell>
</relcell>
</relrow>
</reltable>
<!--EVERYTHING BELOW THIS LINE IS GENERATED AUTOMATICALLY BY CONTEXTUALIZE.XSL.
MANUAL CHANGES WILL BE OVERWRITTEN-->
</map><?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet type="text/xsl" href="xsl/contextualize.xsl"?>
<!DOCTYPE task PUBLIC "urn:pubid:org.kuali.kits.kms:doctypes:dita:task"
"http://www.indiana.edu/~worklist/dita-prototypes/org.kuali.kits.kms/doctypes/task/dtd/kbtask.dtd">
<task id="kbdoc">
<title>How do I use the Subversion DITA repository?</title>
<shortdesc>Connect to the Subversion repository and check out DITA docs using Oxygen's Subversion client</shortdesc>
<prolog>
<author>jorahood</author>
<critdates>
<created date="2010-03-11"/>
<revised modified="2011-10-19"/>
</critdates>
<docid id="bawf"/>
</prolog>
<taskbody>
</taskbody>
</task><?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE map
PUBLIC "-//OASIS//DTD DITA Map//EN" "http://docs.oasis-open.org/dita/v1.2/os/dtd1.2/technicalContent/dtd/map.dtd">
<map id="kbdocmap">
<topicgroup id="docidbox"><topicref audience="default" keys="bawf" href="bawf.dita" id="docid"/></topicgroup>
<reltable>
<relheader>
<relcolspec linking="sourceonly">
<title>Source</title>
</relcolspec>
<relcolspec linking="targetonly">
<title>Refs</title>
</relcolspec>
</relheader>
<relrow>
<relcell>
<topicref keyref="bawf"/>
</relcell>
<relcell>
</relcell>
</relrow>
</reltable>
<!--EVERYTHING BELOW THIS LINE IS GENERATED AUTOMATICALLY BY CONTEXTUALIZE.XSL.
MANUAL CHANGES WILL BE OVERWRITTEN-->
<topicref href="deny.dita"/>
</map><?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE task PUBLIC "urn:pubid:org.kuali.kits.kms:doctypes:dita:task" "http://www.indiana.edu/~worklist/dita-prototypes/org.kuali.kits.kms/doctypes/task/dtd/kbtask.dtd">
<task id="kbdoc">
<title id="default">In Oxygen XML Editor, how do I add a new document to the DITA KB?</title>
<shortdesc>Adding a new document to the DITA KB using Oxygen</shortdesc>
<prolog>
<author></author>
<critdates>
<created date=""/>
<revised modified=""/>
</critdates>
<metadata>
<keywords>
<keyword></keyword>
</keywords>
</metadata>
<docid id="bawq"/>
</prolog>
<taskbody>
<prereq>You must have checked out the DITA Prototypes repository, and have the DITA KB Oxygen
project open in Oxygen Editor. For instructions, see <kba keyref="bawf"/>
</prereq>
<steps>
<step>
<cmd>In the <wintitle>Project</wintitle> window, open the <uicontrol>dmm3</uicontrol>
folder.</cmd>
</step>
<step>
<cmd>Select <menucascade>
<uicontrol>File</uicontrol>
<uicontrol>New...</uicontrol>
</menucascade>
</cmd>
</step>
<step>
<cmd>In the <wintitle>New</wintitle> window, in the text box that says <systemoutput>Type
filter text</systemoutput>, type <uicontrol>kbtopic</uicontrol> and press Enter.</cmd>
</step>
<step>
<cmd>Select <menucascade>
<uicontrol>File</uicontrol>
<uicontrol>Save</uicontrol>
</menucascade>
</cmd>
</step>
<step>
<cmd>Enter the four-letter docid for the topic.</cmd>
</step>
<step>
<cmd>Verify that the <systemoutput>dmm3</systemoutput> directory is selected to save the
file into and click <uicontrol>Save</uicontrol>.</cmd>
</step>
<step>
<cmd>In the <wintitle>Project</wintitle> window, verify that the new file appears in the
<uicontrol>dmm3</uicontrol> folder. If it doesn't, right-click within the
<wintitle>Project</wintitle> window and select <uicontrol>Refresh</uicontrol>, and it
should appear. </cmd>
</step>
<step><note>There is one indispensible piece of metadata for the topic, and that is the docid.</note>
<cmd>To add the docid to the topic, in the <apiname>prolog</apiname> section, find the <apiname>docid</apiname> element, and enter the four-letter docid in the "id" attribute.</cmd></step>
<step>
<cmd>Save the file.</cmd>
</step>
</steps>
<result>The new file is now saved on the server and added to the Oxygen project.</result>
</taskbody>
</task><?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE map
PUBLIC "-//OASIS//DTD DITA Map//EN" "http://docs.oasis-open.org/dita/v1.2/os/dtd1.2/technicalContent/dtd/map.dtd">
<map id="kbdocmap">
<topicgroup id="docidbox"><topicref audience="default" keys="bawq" href="bawq.dita" id="docid"/></topicgroup>
<reltable>
<relheader>
<relcolspec linking="sourceonly">
<title>Source</title>
</relcolspec>
<relcolspec linking="targetonly">
<title>Refs</title>
</relcolspec>
</relheader>
<relrow>
<relcell>
<topicref keyref="bawq"/>
</relcell>
<relcell>
</relcell>
</relrow>
</reltable>
<!--EVERYTHING BELOW THIS LINE IS GENERATED AUTOMATICALLY BY CONTEXTUALIZE.XSL.
MANUAL CHANGES WILL BE OVERWRITTEN-->
<topicref href="deny.dita"/>
<!--from topic: kba or term -->
<topicgroup conref="bawf.ditamap#docidbox"/>
</map>./features/step_definitions/all_steps.rb:316 ./features/step_definitions/all_steps.rb:315:in `/^I should see "([^"]*)" in the preview window$/' features/rendering.feature:299:in `Then I should see "How do I use the Subversion DITA repository?" in the preview window'
314 # from http://blog.kshitizgurung.info/2011/07/detecting-popup-window-and-implementing-test-on-in-capybara-selenium/
315 within_window(page.driver.browser.window_handles.last) do
316 page.should have_content(string)
317 end
318end
In order to arrange documents in useful orders and switch between different orders
As a KMS maintainer
I want to be able to sort the documents in a worklist by any column in ascending and descending order, and by multiple columns
filename | author |
xxxb | bob |
xxxa | andy |
xxxc | chuck |
(eval):2:in `send' (eval):2:in `find' ./features/step_definitions/web_steps.rb:14:in `with_scope' ./features/step_definitions/web_steps.rb:108:in `/^(?:|I )should see "([^"]*)"(?: within "([^"]*)")?$/' features/sorting-a-worklist.feature:22:in `And a worklist exists with id 3090'
0# Couldn't get snippet for (eval)filename |
xxxa |
xxxb |
xxxc |
filename | author |
xxxa | andy |
xxxb | bob |
xxxc | chuck |
filename | author |
xxxc | chuck |
xxxb | bob |
xxxa | andy |
filename | author |
xxxx | bob |
(eval):2:in `send' (eval):2:in `find' ./features/step_definitions/web_steps.rb:14:in `with_scope' ./features/step_definitions/web_steps.rb:108:in `/^(?:|I )should see "([^"]*)"(?: within "([^"]*)")?$/' features/sorting-a-worklist.feature:64:in `And a worklist exists with id 3090'
0# Couldn't get snippet for (eval)filename |
xxxx |
In order to not write the same content twice
As a KB Editor
I want to transclude content from one source to multiple targets
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE task PUBLIC "urn:pubid:org.kuali.kits.kms:doctypes:dita:task"
"http://www.indiana.edu/~worklist/dita-prototypes/org.kuali.kits.kms/doctypes/task/dtd/kbtask.dtd">
<task id="box">
<title id="default">A container task for boilers</title>
<taskbody>
<prereq id="must-create-topic-and-map">Test sentence. You must have created a new topic and its ditamap in the DITA KB.</prereq>
</taskbody>
</task><?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE map
PUBLIC "-//OASIS//DTD DITA Map//EN" "http://docs.oasis-open.org/dita/v1.2/os/dtd1.2/technicalContent/dtd/map.dtd">
<map id="kbdocmap">
<topicgroup id="docidbox"><topicref audience="default" keys="bawt" href="bawt.dita" id="docid"/></topicgroup>
<reltable>
<relheader>
<relcolspec linking="sourceonly">
<title>Source</title>
</relcolspec>
<relcolspec linking="targetonly">
<title>Refs</title>
</relcolspec>
</relheader>
<relrow>
<relcell>
<topicref keyref="bawt"/>
</relcell>
<relcell>
</relcell>
</relrow>
</reltable>
<!-- EVERYTHING BELOW THIS LINE IS GENERATED AUTOMATICALLY BY CONTEXTUALIZE.XSL.
MANUAL CHANGES WILL BE OVERWRITTEN -->
<topicref href="deny.dita"/>
<!-- from topic: boiler -->
<topicgroup conref="boilers-task.ditamap#must-create-topic-and-map"/>
</map><?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE task PUBLIC "urn:pubid:org.kuali.kits.kms:doctypes:dita:task" "http://www.indiana.edu/~worklist/dita-prototypes/org.kuali.kits.kms/doctypes/task/dtd/kbtask.dtd"> <task id="kbdoc"> <title id="default">How do I create Refs for a topic in the DITA KB?</title> <taskbody> <prereq conref="boilers-task.dita#box/must-create-topic-and-map"/> </taskbody> </task>
./features/step_definitions/all_steps.rb:316 ./features/step_definitions/all_steps.rb:315:in `/^I should see "([^"]*)" in the preview window$/' features/transclusion.feature:67:in `Then I should see "You must have created a new topic and its ditamap in the DITA KB." in the preview window'
314 # from http://blog.kshitizgurung.info/2011/07/detecting-popup-window-and-implementing-test-on-in-capybara-selenium/
315 within_window(page.driver.browser.window_handles.last) do
316 page.should have_content(string)
317 end
318end
In order to add to existing documents
As a KMS Maintainer
I want to be able to modify existing documents
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "http://docs.oasis-open.org/dita/v1.1/OS/dtd/topic.dtd">
<topic id="kbdoc" xml:lang="en-us">
<title>Shopping for groceries</title>
<body>
<p>A sample document to test ditac rendering.</p>
</body>
</topic><?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "http://docs.oasis-open.org/dita/v1.1/OS/dtd/topic.dtd">
<topic id="kbdoc" xml:lang="en-us">
<title>Shopping for groceries</title>
<body>
<p>A simple document to test ditac rendering.</p>
</body>
</topic>features/visibility-filtering.feature:7:in `Given a document with visibility of "visible"'
5Scenario: As an un-logged-in end-user, I can search for content with visibility = visible
6
7Given a document with visibility of "visible"
8When I search the KB for the document
9Then I should see the document in the resultsGiven /^a document with visibility of "([^"]*)"$/ do |arg1| pending # express the regexp above with the code you wish you had end
features/visibility-filtering.feature:8:in `When I search the KB for the document'
6
7Given a document with visibility of "visible"
8When I search the KB for the document
9Then I should see the document in the resultsWhen /^I search the KB for the document$/ do pending # express the regexp above with the code you wish you had end
features/visibility-filtering.feature:9:in `Then I should see the document in the results'
7Given a document with visibility of "visible"
8When I search the KB for the document
9Then I should see the document in the results
10
11Scenario: As an un-logged-in end-user, I cannot search for content with visibility = invisibleThen /^I should see the document in the results$/ do pending # express the regexp above with the code you wish you had end
features/visibility-filtering.feature:13:in `Given a document with visibility of "invisible"'
11Scenario: As an un-logged-in end-user, I cannot search for content with visibility = invisible
12
13Given a document with visibility of "invisible"
14When I search the KB for the document
15Then I should not see the document in the resultsGiven /^a document with visibility of "([^"]*)"$/ do |arg1| pending # express the regexp above with the code you wish you had end
features/visibility-filtering.feature:14:in `When I search the KB for the document'
12
13Given a document with visibility of "invisible"
14When I search the KB for the document
15Then I should not see the document in the resultsWhen /^I search the KB for the document$/ do pending # express the regexp above with the code you wish you had end
features/visibility-filtering.feature:15:in `Then I should not see the document in the results'
13Given a document with visibility of "invisible"
14When I search the KB for the document
15Then I should not see the document in the results
16
17Scenario: As an un-logged-in end-user, I cannot search for but can see content with visibility = draftThen /^I should not see the document in the results$/ do pending # express the regexp above with the code you wish you had end
features/visibility-filtering.feature:19:in `Given I am not logged in'
17Scenario: As an un-logged-in end-user, I cannot search for but can see content with visibility = draft
18
19Given I am not logged in
20Given a document with visibility of "draft"
21When I search the KB for the documentGiven /^I am not logged in$/ do pending # express the regexp above with the code you wish you had end
features/visibility-filtering.feature:20:in `Given a document with visibility of "draft"'
18
19Given I am not logged in
20Given a document with visibility of "draft"
21When I search the KB for the document
22Then I should not see the document in the resultsGiven /^a document with visibility of "([^"]*)"$/ do |arg1| pending # express the regexp above with the code you wish you had end
features/visibility-filtering.feature:21:in `When I search the KB for the document'
19Given I am not logged in
20Given a document with visibility of "draft"
21When I search the KB for the document
22Then I should not see the document in the results
23But I should be able to open the document in the KB.When /^I search the KB for the document$/ do pending # express the regexp above with the code you wish you had end
features/visibility-filtering.feature:22:in `Then I should not see the document in the results'
20Given a document with visibility of "draft"
21When I search the KB for the document
22Then I should not see the document in the results
23But I should be able to open the document in the KB.
24And the document should say "DRAFT" in front of the titleThen /^I should not see the document in the results$/ do pending # express the regexp above with the code you wish you had end
features/visibility-filtering.feature:23:in `But I should be able to open the document in the KB.'
21When I search the KB for the document
22Then I should not see the document in the results
23But I should be able to open the document in the KB.
24And the document should say "DRAFT" in front of the titleThen /^I should be able to open the document in the KB\.$/ do pending # express the regexp above with the code you wish you had end
features/visibility-filtering.feature:24:in `And the document should say "DRAFT" in front of the title'
22Then I should not see the document in the results
23But I should be able to open the document in the KB.
24And the document should say "DRAFT" in front of the title
25
26Scenario: As an un-logged-in end-user, I cannot search for but can see content with visibility = nosearchThen /^the document should say "([^"]*)" in front of the title$/ do |arg1| pending # express the regexp above with the code you wish you had end
features/visibility-filtering.feature:28:in `Given I am not logged in'
26Scenario: As an un-logged-in end-user, I cannot search for but can see content with visibility = nosearch
27
28Given I am not logged in
29Given a document with visibility of "draft"
30When I search the KB for the documentGiven /^I am not logged in$/ do pending # express the regexp above with the code you wish you had end
features/visibility-filtering.feature:29:in `Given a document with visibility of "draft"'
27
28Given I am not logged in
29Given a document with visibility of "draft"
30When I search the KB for the document
31Then I should not see the document in the resultsGiven /^a document with visibility of "([^"]*)"$/ do |arg1| pending # express the regexp above with the code you wish you had end
features/visibility-filtering.feature:30:in `When I search the KB for the document'
28Given I am not logged in
29Given a document with visibility of "draft"
30When I search the KB for the document
31Then I should not see the document in the results
32But I should be able to open the document in the KB.When /^I search the KB for the document$/ do pending # express the regexp above with the code you wish you had end
features/visibility-filtering.feature:31:in `Then I should not see the document in the results'
29Given a document with visibility of "draft"
30When I search the KB for the document
31Then I should not see the document in the results
32But I should be able to open the document in the KB.Then /^I should not see the document in the results$/ do pending # express the regexp above with the code you wish you had end
features/visibility-filtering.feature:32:in `But I should be able to open the document in the KB.'
30When I search the KB for the document
31Then I should not see the document in the results
32But I should be able to open the document in the KB.
33
34 Then /^I should be able to open the document in the KB\.$/ do pending # express the regexp above with the code you wish you had end
In order to handle projects that require editing an ad hoc group of documents
As a KB Maintainer
I want the system to incorporate docs into lists that I can interact with